Add Argon2 (RFC 9106) to Cryptography Registry#793
Add Argon2 (RFC 9106) to Cryptography Registry#793Mehrn0ush wants to merge 3 commits intoCycloneDX:masterfrom
Conversation
|
The primitive for the variant Argon2(id|i|d)[-{memoryKiB}][-{passes}][-{parallelism}] should be kdf. Also, the variable {dkLen} may be considered. |
Updated Argon2 variant primitive to kdf and added optional [-{dkLen}] for derived key length, consistent with existing {dkLen} usage in the registry. |
Add Argon2 (RFC 9106) to the Cryptography Registry with a parameterized pattern aligned to RFC terminology. Signed-off-by: Mehrn0ush <[email protected]>
Signed-off-by: Mehrn0ush <[email protected]>
95e1727 to
28eacb1
Compare
|
Added Argon2 to schema/cryptography-defs.schema.json#/definitions/algorithmFamiliesEnum to keep the schema enum aligned with the registry data in schema/cryptography-defs.json. |
Signed-off-by: Mehrn0ush <[email protected]>
520e69f to
48455b8
Compare
|
I noticed schema/cryptography-defs.schema.json did not end with a trailing newline in the current base. |
This PR adds Argon2 (RFC 9106) to
schema/cryptography-defs.json.Notes on parameter naming vs Issue #756
Issue #756 proposes:
Argon2(id|i|d)[-{memoryMiB}][-{iterations}][-{parallelism}].RFC 9106 defines:
mas memory size in kibibytes (KiB),tas number of passes,pas degree of parallelism.Accordingly, this PR uses:
Argon2(id|i|d)[-{memoryKiB}][-{passes}][-{parallelism}]If the community prefers the Issue's naming for consistency with existing conventions, I can update the pattern accordingly.
Refs: #756